Fix container death after smbd initializes. #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've seen this in a couple different rpi-samba images. Basically something like this happens:
This fixes the issue, somehow - thanks to this stack exchange article: http://unix.stackexchange.com/a/277119
After building the image -- you can pull it via
docker pull charlesmknox/rpi-samba
if you want to test -- the container no longer exits with code 0:The fix is simply to append
< /dev/null
to the last line in/run.sh
. Why does this work? I don't know. But it works, and on top of that, my share works too!